QRZ! Ham Radio 4/QRZ Ham Radio Callsign Database - Volume 4.iso/digests/digital/940219.txt

Internet Message Format | 1994-11-13 | 14KB

Date: Wed,  6 Jul 94 04:30:21 PDT
From: Ham-Digital Mailing List and Newsgroup <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: Ham-Digital Digest V94 #219
To: Ham-Digital


Ham-Digital Digest          Wed,  6 Jul 94       Volume 94 : Issue  219

Today's Topics:
                 AEAFAX II:  Junk or merely mediocre?
                       Camcorder viewer needed.
                   G3RUH modem - tech description.
                    Help please - Packet & TCP/IP
               N0ARY Packet BBS or other for Linux/Unix
                    Q: MFJ 1278B Multi-Controller
              Questions regarding WAMPES under Sun/SunOS
                          TAPR PSR Deadline
                     Troubleshooting Tips Needed

Send Replies or notes for publication to: <[e-mail]>
Send subscription requests to: <[e-mail]>
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the Ham-Digital Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives/ham-digital".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: 5 Jul 94 21:45:21 GMT
From: ihnp4.ucsd.edu!swrinde!howland.reston.ans.net!noc.near.net!news.delphi.com!BIX.com![e-mail]
Subject: AEAFAX II:  Junk or merely mediocre?
To: [e-mail]

Just got back from picking up a copy of AEAFAX II from Ham Radio
Outlet.  But even though it's not a particularly expensive package,
it's not obvious to me that it's worth the money.  Call me old-
fashioned, but I kind of expect things to work.

I tried initially running it in the DOS box under OS/2 1.3 on my
386-based PS/2 Model 80.  Installation went okay, but when I tried
to run it, it aborted with only the messsage, "Serial port not
fitted.  Aborting."  Manually specifying a com port, verifying the
port is visible to the DOS box, etc., had no effect.

I then tried it on my DEC Alpha running Windows NT.  It came up and
did run (sort of) but not without problems.  The text menu display
was garbled with random garbage characters and the more I moved
around on the the menu, the more garbage I got.  You're supposed
to be able to push F1 for help, but doing so caused it to paint
and then immediately clear away the menu so fast it could not
possibly be read.  (It's supposed to stay up until you press another
key.)

Okay, you say, this is sort of explainable since AEAFAX is really
supposed to be a DOS program.  So even though I really had bought
it hoping to run it under OS/2 or NT -- I just *never* run DOS
these days -- I decided to give it one last shot, booting my PS/2
in genuine DOS 5.0.

Didn't work.  The program comes up, but when you try to display
one of their sample FAXes, it paints only 1/2 the image.

I tried calling AEA's Customer Service line, ended up waiting about
10 minutes or so on hold ("Your call will be answered in the order
received") and gave up.

On top of that, the whole interface/design is really crude.  It's
going back.  I don't care what HRO wants to tell me about SW not
being returnable.  For me, it didn't work.

OTOH, it does raise the question:  is there anything out there that
does do weather FAX decently?

Regards,
Doug Hamilton    KD1UJ    [e-mail]    Ph 508-358-5715
Hamilton Laboratories, 13 Old Farm Road, Wayland, MA  01778-3117, USA

------------------------------

Date: 5 Jul 1994 23:19:49 -0700
From: nntp.crl.com!crl.crl.com![e-mail]
Subject: Camcorder viewer needed.
To: [e-mail]

Hello all-

I am interested in making some "VR" glasses except instead of using small
computer screens or whatever they are, I would like to use the small
screen that is looked into when you use a camcorder.  Does anybody have
any idea where I could obtain these?  I would appreciate addresses,
phone#'s, and, prices.  Thanx in advance.

------------------------------

Date: 6 Jul 94 10:27:46 NZST
From: ihnp4.ucsd.edu!usc!howland.reston.ans.net!wupost!waikato!comp.vuw.ac.nz!newshost.wcc.govt.nz!kosmos.wcc.govt.nz![e-mail]
Subject: G3RUH modem - tech description.
To: [e-mail]

Can anyone tell me please, whether a full technical description
of the G3RUH 9600 baud modem has been published in Wireless World
(and its successors), in QST, in Radio Communications, or any
other similar electronics journal.

If so, could I please have a reference to the article (journal
and date of publication.

Thanks in advance.

Jim.
[e-mail]
ZL2APE@ZL2WA.#60.WLG.NZL.OC

------------------------------

Date: Tue, 05 Jul 1994 22:01:31 +0400
From: ihnp4.ucsd.edu!usc!sol.ctr.columbia.edu!news.mtu.edu!DialupNewsWatcher![e-mail]
Subject: Help please - Packet & TCP/IP
To: [e-mail]

In article <[e-mail]>, [e-mail] (Ian
Gillingham) wrote:

> First of all, I appologise if this is already a FAQ somewhere, but I
> couldn't see it.
>
> I am relatively new to packet and using an MFJ1274 - TNC2 clone.
> Wish I'd got into packet years ago, as I'm only just realising the
> level of connectivity offered.  Anyway, being an Internet fan (adict?)
> I quite naturally picked up on the fact that some of us are using TCP/IP
> software with TNC's instead (as well as) the usual simple terminal
> packages being used by amateurs like myself.
>
> My TNC has KISS mode available and I've downloaded and used the KA9Q NOS
> TCP/IP prog.  I have managed, through trial & error to attach to my COM2
> serial port with:
>      ax25 mycall G0FLB
>      attach asy 0x2f8 3 ax25 ax0 1024 576 9600
> I have even managed to make an initial connection to a local digipeater,
> but once connected, I don't see any text etc..
> I DO see stations using the 'ax25 heard ax0' command.
>
> What do I do next ?
> What are the benefits ?
> What am I doing wrong ?
> Why am I so ignorant ??
>

You just need to turn on the trace function. Put a line in your
autoexec.nos
file(or just type it in from the > prompt) such as:
    trace ax0 0111
That will turn on tracing for the ax0 port and monitor all incoming and out
going packets.
    I had the same problem when I first started using nos, it seemed to
take
forever to learn how to just do simple things. Stick with it, all of the
work
to learn this program is worth it!! I have had many happy hours of learning
about tcp/ip and the price is right!!

------------------------------

Date: 6 Jul 1994 05:44:52 GMT
From: ihnp4.ucsd.edu!usc!nic-nac.CSU.net!charnel.ecst.csuchico.edu![e-mail]
Subject: N0ARY Packet BBS or other for Linux/Unix
To: [e-mail]

Hello everyone!  I just set up Linux and Dos on my system.
I am currently running a very small NOS system on Dos for a local
packet bbs.  I was wondering if anyone know of some good packet
software for Linux/Unix?  I heard N0ARY made some good stuff, I was
on there mailing list but dunno what happend, haven't heard anything
for a while.  If anyone knows where I can get the files for the N0ARY
packet bbs software, some doc's on it, and even possibly some setup
help, please mail me back!  I don't read the news group too often yet,
but will start, so I may miss your reply if you post it here..

Thanks..
    Paul, KD6DZP @ Chico California
73's..

------------------------------

Date: 5 Jul 94 11:46:21 EDT
From: ihnp4.ucsd.edu!swrinde!howland.reston.ans.net!noc.near.net!usenet.elf.com!rpi!psinntp!main03![e-mail]
Subject: Q: MFJ 1278B Multi-Controller
To: [e-mail]

In article <[e-mail]> [e-mail] (Torsten Leibold) writes:

Regarding the MFJ 1278B
>Can anyone tell me his/her experiences with this controller ??
>I thought about purchasing one, but for it's my first 'Multi' I'm not
>quite sure which one to choose. I would mainly use it for
>rtty/amtor/pactor - no pr ...
>Do you think it's ok ?

I bought a 1278 used almost a year ago. Has been fine. Works well in all modes.
Have used it with a dumb terminal, the Lanlink demo, NOS and Keaterm.
Mine is an early one and doesn't have PACTOR. I've used it for packet both in
AX25 and KISS mode for TCP/IP. It IS kind of noisy though. There's a harmonic
that falls around 145mhz that you can move slightly by pulling the clock with
an internal trimmer cap. I'm upgrading it with a 2400 baud modem now.
Joe - AA3GN
--
Joe Landis - System & Network Mgr. - North American Drager Co. Telford, PA
[e-mail] | uupsi5!main03!landisj | AA3GN@WB3JOE.#EPA.PA.USA
Opinions are mine only, and do not reflect those of my employer.

------------------------------

Date: 5 Jul 1994 20:54:15 GMT
From: ihnp4.ucsd.edu!swrinde!howland.reston.ans.net!sol.ctr.columbia.edu!news.cs.columbia.edu!news.boxhill.com!boxhill![e-mail]
Subject: Questions regarding WAMPES under Sun/SunOS
To: [e-mail]

Perhaps the collective out there can offer advice:

I've just installed Wampes (NOS, sorta, for UNIX, FYI) on my Sun SPARCstation
running SunOS 4.1.3, and have successfully telnetted, pinged, ftp'd to a few
other sites near me.  So far, very nice!

Is there any way of more tightly integrating wampes' (aka net>) IP networking layers
into those of SunOS?  Specifically, is there any way to make wampes appear
as a routable network interface under SunOS?
In this way, I could telnet (or ftp or whatever) 44.xx.xx.xx *FROM SUNOS DIRECTLY*
rather than from the "net" or "cnet" front-end.  All I would have to do is
add a route such as: # route add net 44.0.0.0 mysun 1.

Similarly, could wampes understand incoming IP packets on ax0 which are addressed
to my interface (N2TIA under AX.25, as I understand it)
but whose destination IP address is not necessarily 44.anything,
and pass such packets to SunOS's network layers for routing?
In this way, I could theoretically telnet (or ftp or whatever) any Internet
address from another 44.xxx.xxx.xxx station by routing the packets to N2TIA.ampr.org
for further routing.

I noticed that wampes comes with code for many of the usual ftp clients and listeners
(such as telnet, ftp, ping, etc) which get linked into itself (net>), and thought
that this seemed like such a duplication of effort since all these services are
already running and listening under SunOS (or any UNIX) to begin with.
Wampes really should only be a network interface to UNIX, not a whole
TCP swiss army knife, no?
(I'm aware of things like NET/ROM support and plain AX.25 connection support in
wampes also, which are much appreciated. My comments apply only to the IP parts)

I'm a newbie to TCP/IP over packet, but have a respectable amount of experience with
IP in UNIX (hardwired) networks, and a modest amount of experience with plain
AX.25 packet operation.

Am I missing something here?

Thanks in advance to anyone who can offer nuggets of advice.

I'd appreciate a cc to [e-mail] of any reply postings.

73!
Ken Stamm  N2TIA             BBBB          H  H  i  ll  ll
([e-mail])            B   B         H  H      l   l
BoxHill Systems Corporation  BBBB  ooo x x HHHH ii   l   l
161 Avenue of the Americas   B   B o o  x  H  H  i   l   l
New York, NY 10013           BBBB  ooo x x H  H iii lll lll
Tel: (212)989-HILL (4455)
Fax: [phone]        S y s t e m s C o r p o r a t i o n

------------------------------

Date: 6 Jul 1994 01:56:43 GMT
From: ihnp4.ucsd.edu!usc!cs.utexas.edu!news.unt.edu!tcet.unt.edu![e-mail]
Subject: TAPR PSR Deadline
To: [e-mail]

Deadline for articles and submissions for the Summer issue of the TAPR
Packet Status Register is this week (ending 7/8/94).

If you have news, information, or articles, direct them to Bob Hansen
[e-mail]

Regional packet groups are invited to submit short information
blurbs on current development and direction.

For more information, contact Bob Hansen.

------------------------------------------------------------------------
Tucson Amateur Packet Radio
8987-309 E Tanque Verde Rd #337 * Tucson, Az * 85749-9399 * 817-383-0000

------------------------------

Date: 5 Jul 1994 18:53:50 -0500
From: swrinde!howland.reston.ans.net!vixen.cso.uiuc.edu!newsfeed.ksu.ksu.edu!moe.ksu.ksu.edu!hobbes.physics.uiowa.edu!news.uiowa.edu!blue.weeg.uiowa.edu!blue.weeg.uiowa.edu!@@ihnp4.ucsd.edu
Subject: Troubleshooting Tips Needed
To: [e-mail]

I'm trying to get some equipment together and am getting pretty
frustrated.  I need some help in good troubleshooting techniques, or
tips on what I mgiht be overlooking.

I have a Ramsey 2m FX 146 that I've used on voice and radio OK, but not
totally trouble free.  I'm running it thorugh a Ramsey kit Baycom modem
that I've never really gotten running.  I'm using Baycom.  I have talked
on the radio through repeaters and it seems to transmit and receive alright,
though I won't vouch for the power or purity.

I've run it on a Packkit 232 and am able to receive packets, but apparently
when I send them I don't get out right OR I dont' get an answer back from the
station called.  Using the Baycom setup I get all the indications of sending
and recieving, but no messages or connect signs show up on the computer.

I'm about ready to pull my hair out.  I've checked and double checked the
components, including solder joints, but am not sure of just what I need to
do to get the trouble down to one component.

I knwo this is kind of a shotgun request, but if anyone has any tips
I'd be much obliged.


--

Jim - Farmer - Iowa City, IA,

------------------------------

End of Ham-Digital Digest V94 #219
******************************